-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Fix handling of circular MOVED redirects in cluster slot mapping #3899
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Hi, I’m Jit, a friendly security platform designed to help developers build secure applications from day zero with an MVS (Minimal viable security) mindset. In case there are security findings, they will be communicated to you as a comment inside the PR. Hope you’ll enjoy using Jit. Questions? Comments? Want to learn more? Get in touch with us. |
… the redirected node is already the shard primary.
d6c72b1 to
5361dc1
Compare
|
Hi @barshaul, thank you for your contribution. We will review it soon. |
Thanks |
c446c1e to
b2b314b
Compare
|
@petyaslavova ready for another round |
petyaslavova
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thank you @barshaul !
Description of change
Circular MOVED responses were incorrectly treated as failover events, causing the
primary node to be demoted and leaving shards with replicas only.
This can occur in DNS-based environments where a MOVED response intentionally
points back to the same address (e.g., MOVED + disconnect to force DNS re-resolution).
This change detects circular MOVED redirects and avoids updating the slot map
when the redirected node is already the shard primary.
Pull Request check-list
Please make sure to review and check all of these items: